docs(inkless:design): add diskless-managed rf feature design #478
Conversation
There was a problem hiding this comment.
Pull request overview
This PR adds a comprehensive design document for implementing managed replication factor (RF) for diskless topics in the Inkless system. The document proposes transitioning from the current RF=1 with faked metadata to RF=rack_count with real KRaft-managed replicas, enabling bidirectional topic migration and standard RLM integration.
Changes:
- Adds new
DISKLESS_MANAGED_RF.mddesign document with detailed approach comparison, cost analysis, and implementation plan - Updates
DESIGN.mdto reference the new design document for Stream 4: Multi-Replica Model for Diskless Topics
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 1 comment.
| File | Description |
|---|---|
| docs/inkless/ts-unification/DISKLESS_MANAGED_RF.md | New comprehensive design document proposing RF=rack_count approach with transformer-first availability, including motivation, design details, implementation path (6-8 weeks), and rejected alternatives |
| docs/inkless/ts-unification/DESIGN.md | Adds cross-references to the new DISKLESS_MANAGED_RF.md document in the Multi-Replica Model section and References section |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
|
|
||
| | Trade-off | Accepted | Rationale | | ||
| |-----------|----------|-----------| | ||
| | KRaft metadata may show offline brokers | Yes | Availability is not blocked; eventual consistency is acceptable | |
There was a problem hiding this comment.
KRaft metadata may show offline brokers
Internally or to the clients?
There was a problem hiding this comment.
To admin operations/metrics (e.g. topic describe), not to clients.
I'll clarify this
Ensure cross-az is the last resort when routing requests, and that replica placement is fully decoupled.
|
Moving it to draft to keep it as a live doc while this feature is developed. |
No description provided.